StarCommand can no longer communicate with this device. Either the device has been turned off or the communication path to StarCommand is broken.
StarCommand is now back in contact with the device.
StarCommand has detected an autopartitioned port for the device. This can be caused by a jam or by excessive noise (fragments). If the autopartition persists, check the nodes on this port for the source.
The device’s port is no longer autopartitioned.
The device was unable to test the port at this time. This is usually due to high traffic. Try again.
StarCommand can no longer communicate with this device because the communication configuration does not allow it.
StarCommand is now back in contact with this device.
The displayed port enable settings were not consistent with the current hardware state and have been adjusted accordingly. Communication problems or another person running StarCommand may have caused the discrepancy.
The displayed port interconnect settings were not consistent with the current hardware state and have been adjusted accordingly. Communication problems or another person running StarCommand may have caused the discrepancy.
The displayed link integrity settings were not consistent with the current hardware state and have been adjusted accordingly. Communication problems or another person running StarCommand may have caused the discrepancy.
This device has been reset. This is caused by a power interruption or by a Reset command from StarCommand. Resets can cause short interruptions in the network.
This device has now been successfully reprogrammed.
This device could not be reprogrammed. This is usually caused by a defect in the program chip or a failure during device reprogramming.
The reprogramming of this device has been cancelled.
This device is incorrectly programmed. This is usually caused by a defect in the program chip or a failure during device reprogramming.
Unknown Error 16
Unknown Error 17
Unknown Error 18
Click on an entry in the list below to get more information.
An unknown Router event has occurred.
This device has been started using the current code & data memory images.
This device has been started reloading the code & data memory images from configured boot source.
Bad Buffer List
The device has detected an error in the code memory image. A new image has been reloaded from Flash EPROM.
Bad Data CRC
This device has detected an error in the hardware interrupt circuitry. Please contact Farallon Technical Support.
This device has detected an error in the hardware DMA circuitry. Please contact Farallon Technical Support.
This device was unable to transmit a packet. This can be caused by an unusually high level of network traffic.
This device has completed the Console Initialization procedure.
This device was unable to find a BOOTP server.
This device was unable to find the TFTP server.
The TFTP server was unable to find the download image file for this device.
The TFTP server was not able to access the download image file for this device.
A TFTP packet was received with an invalid transaction ID.
The downloaded file is not a valid firmware image format.
This device was unable to reprogram its flash EPROM. Please contact Farallon Technical Support.
The downloaded file is too large for the available RAM in this device. Please contact Farallon Technical Support.
An unknown TFTP error has been detected. Please contact Farallon Technical Support.
This device’s flash EPROM was successfully reprogrammed with new firmware.
The device’s IPTalk configuration is invalid. The device may have been configured by software that doesn’t have StarCommand’s configuration error checking.
This device was unable to allocate memory for an IPTalk routing table entry.
This device was unable to allocate an IP packet.
IPTalk initialized using NIC assigned UDP ports.
IPTalk initialized using KIP UDP ports.
The device received an IPTalk packet with an unknown network number. There may a problem with the device that sent the packet.
The device received an invalid IPTalk packet from an IP host. There may a problem with the IP host that sent the packet.
The device could not allocate enough memory for an AppleTalk packet. There may be a problem with the device’s memory. Contact Farallon Technical Support.
The device has started downloading atalkad routing information from the atalkad server.
The device has successfully downloaded routing information from the atalkad server.
The device received a restart command from the atalkad server.
The device received an atalkad packet of an unknown type.
There may be a problem with the host.
The device received an invalid atalkad packet. There may be a problem with the host.
The device received a packet addressed to a network that is not listed in the device’s routing table. There may be a problem with the IPTalk configuration.
The device received an invalid atalkad packet. There may be a problem with the atalkad server.
There may be a problem with the host’s IPTalk configuration or the host may not be running an IPTalk process.
There may be a problem with the host’s atalkad process. Make sure that the host is properly configured as an atalkad server.
The network was removed from the device’s routing table because the device hasn’t heard about the network for five minutes.
This device can now receive and transmit AppleTalk packets.
This device has aquired an AppleTalk node on a non-extended port.
This device has aquired an AppleTalk address on an extended port.
This device has completed the network seeding process on all enabled ports.
This AppleTalk non-extended interface to the network is fully operational.
This AppleTalk extended interface to the network is fully operational.
This device detected a conflict in the AppleTalk configuration and will restart using the correct network information.
This device has detected a failure in the system timer. Please contact Farallon Technical Support.
This device has detected a failure in the timer interrupt curcuitry. Please contact Farallon Technical Support.
This device has detected a failure in the LocalTalk serial controller. Please contact Farallon Technical Support.
This device has detected a failure in the RAM circuitry. Please contact Farallon Technical Support.
This device has detected a failure in the flash EPROM circuitry. Please contact Farallon Technical Support.
CRC Error in the code RAM. Please consult your FE
A critical section of the diagnostic tests was interrupted. The configuration will revert to the factory settings.
The device received a reset command from StarCommand.
An autopartitioned port has been detected. This can be caused by a jam or by noise (fragments). If it persists, check the nodes on this port for the source.
The device’s port is no longer autopartitioned.
Statistics version conflict, clearing all statistics
Configuration version conflict, reverting to defaults
The specified subnet mask is not consistent with the indicated IP address.
